If you are a scripter, you've done your own basic debugging by inserting "wait until the mouseclick" and "put varible1 into msg" commands after lines of code where you suspected a bug. Many times this works fine but it's very time consuming to put all the commands in and then take them all out. It is also difficult to track more that 2 or 3 variables at a time. It is this process which Hyperbug simplifies.
Hyperbug was created to be a simple and quick way to step through a chosen range of Hypertalk code in any Hypercard object and track user defined variables, Hypertalk functions, properties and containers.
The limitations with this type of debugger are that you cannot debug a script that physically goes to other cards or stacks. But, since most scripting problems occure in a small range of code within one object, Hyperbug does fill a large need for all Hypertalk programmers.
Hyperbug does it's best work debugging complicated control structures such as deeply nested repeat loops with if/then/else controls. It is also great for stepping through on card animation and keeping track of Hypertalk properties and functions like; The Params, the stackspace, the heapspace and the freesize.
All actions to setup, operate and abort the debugging process are performed by clicking on the 7k Hyperbug Button or by clicking on the Hyperbug Button in conjunction with the keyboard commands (command,shift or option.) This keeps screen clutter to a minimum.
